new landing page #2078
new landing page #2078
Conversation
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
* Extract edges and boxes out from the components. * Make diagram boxes and edges responsive * Make the diagram less tall * Animate client edge on small screens * Animate server edges on small screens * Remove next step on background click per Uri's request * Rotate query sideways on small screens
Co-authored-by: Benjie <benjie@jemjie.com>
|
Hey @benjie, I've applied your suggestions, so we're down to #2078 (comment) Could you tell me if the texts in the green use cases section are okay? 
I'm also not sure about this:
I know I'm being annoying, but GraphQL spec defines a type system, right? The service defines data types with a schema. |
Co-authored-by: Jeff Auriemma <bignimbus@users.noreply.github.com>
* Add [Try it out] link to the Hero * Add redirect from /docs to /learn
| "Deliver high-performance user experience at any scale", | ||
| "Secure and stabilize your API with a strongly typed schema and validated requests", | ||
| "Reduce communication overhead through efficient, distributed development", |
There was a problem hiding this comment.
I'm late to the party but this is a lot of words for my limited brain. Proposal for simplification:
| "Deliver high-performance user experience at any scale", | |
| "Secure and stabilize your API with a strongly typed schema and validated requests", | |
| "Reduce communication overhead through efficient, distributed development", | |
| "High-performance at any scale", | |
| "Typesafe schemas, secure requests", | |
| "Frictionless distributed development", |
My logaf is low and this has probably been bikeshedded already, feel free to discard my comment.
There was a problem hiding this comment.
I love the shortening
the first sentence though was suppose to talk about creating UI at scale, like data co-location stuff
I wonder how we can capture that in a short sentence?
There was a problem hiding this comment.
New attempt with Data driven UI at scale
| "Deliver high-performance user experience at any scale", | |
| "Secure and stabilize your API with a strongly typed schema and validated requests", | |
| "Reduce communication overhead through efficient, distributed development", | |
| "Typesafe schemas, secure requests", | |
| "Frictionless distributed development", | |
| "Data driven UI at scale", |
I am also moving it last because it's a consequence of the first two IMO. If I'm coming to graphql.org and the first thing I see is about UIs, it would have tripped me up.
| GraphQL is an open‑source query language for APIs and | ||
| a server‑side runtime. It provides a strongly‑typed schema to | ||
| define relationships between data, making APIs more flexible and | ||
| predictable. And it isn’t tied to a specific database or storage |
There was a problem hiding this comment.
| predictable. And it isn’t tied to a specific database or storage | |
| predictable. GraphQL isn’t tied to a specific database or storage |
learn — restyled left sidebar
Co-authored-by: Martin Bonnin <martin@mbonnin.net>
Co-authored-by: Martin Bonnin <martin@mbonnin.net>
Co-authored-by: Martin Bonnin <martin@mbonnin.net>
Description
Howdy. I updated the landing page according to the new designs discussed in graphql/community-wg#21.
If you're interested in reading it step by step in chunks bigger than one commit, you can find the PRs reviewed by @saihaj in my fork hasparus/graphql.github.io/pulls?q=is+new-landing+.